Open
Conversation
nargokul
reviewed
Mar 10, 2026
sagemaker-mlops/src/sagemaker/mlops/feature_store/feature_group.py
Outdated
Show resolved
Hide resolved
sagemaker-mlops/src/sagemaker/mlops/feature_store/feature_group_manager.py
Show resolved
Hide resolved
6f00f8a to
3baff6c
Compare
3baff6c to
e706a5c
Compare
c2df25d to
5cff78d
Compare
fb11c14 to
14cff87
Compare
5ae4c90 to
4f1985d
Compare
- Remove unused datetime imports - Remove debug print statement from resource registration - Update docstring to clarify S3 deny bucket policy is recommended - Refactor error handling to use fail-fast with deferred warnings pattern - Store phase errors instead of immediately raising to allow all phases to attempt execution - Move warning logs before error re-raise so incomplete steps are reported before exception - Simplify phase execution logic by checking phase_error status before attempting each phase - Improve error messages to guide users on re-running the method after fixing issues
nargokul
approved these changes
Apr 14, 2026
mollyheamazon
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds Lake Formation integration to SageMaker Feature Store, enabling customers to govern access to their offline store data through AWS Lake Formation instead of relying solely on IAM policies.
This simplifies the manual process described in this blog
https://aws.amazon.com/blogs/machine-learning/control-access-to-amazon-sagemaker-feature-store-offline-using-aws-lake-formation/
New Features
LakeFormationConfig— declarative configuration for Lake Formation governance:FeatureGroupManager.create()— added lake_formation_config parameterFeatureGroupManager.enable_lake_formation()— new methodEnables Lake Formation on existing Feature Groups
Three-phase setup:
Fail-fast behavior with clear error reporting at each phase
Interactive confirmation prompts warn users about risks (controllable via acknowledge_risk)
Logs recommended S3 deny policy as a warning
Usage
Enable at creation:
Testing
Notes
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.